In response to this:

Refer to RHOAIENG-12337.

This PR adds support for KServe's InferenceLogger TLS CA bundles.

If a KServe InferenceService is deployed in the same namespace as the TrustyAIService, the operator will:

• Check the configured CA bundle for logging in the global KServe inferenceservice-config CM.
• If the there isn't a CA bundle defined, the operator will add a non-TLS logger to the IS (i.e. http://...)
• If there is a CA bundle defined:
• If it is already present in the namespace, will be mounted at /etc/tls/kserve on the service and specified with the env var KSERVE_LOGGER_CA_CERT
• If there is no CA bundle CM defined, it will be created by operator (using OpenShift Serving Certificates) with CM name and CA name as in the global KServe config and mounted on the service as above
• A TLS logger URL will be created (i.e. https://...)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.